No solution here; I still have the same issue on 3 different systems.

   I am not sure if the problem has been acknowledged by the programming
team yet.

   The best clues to figuring out the cause of the problem have been
discovered by Edward Handrich and reported in earlier thread messages:
   -  The lockups occur after a first image has been rendered, at every 32
characters typed
   -  The lockup nails the cpu and lasts for about 4 seconds

   Any chance that the problem will be solved in version 3.6, which should
be out soon?


"James Taylor" <jim### [at] blueyondercouk> wrote in message
news:3fd4cff2$1@news.povray.org...
> I too suffer from this problem - has anyone found a solution yet?
>
> thanks
> jim
>
>

Post a reply to this message